5.3.3 APPX Application Design Manual

+ Chapter 1-1: Overview of Application Design
+ Chapter 1-2: Getting Started
- Chapter 1-3: Data Dictionary
+ Chapter 1-4: Understanding Process Design
+ Chapter 1-5: Interprocess Communication
+ Chapter 1-6: Customizing Your Application
+ Chapter 1-7: The Documentation Facility
+ Chapter 1-8: Application Design Tools
+ Chapter 2-1: Data Dictionary Overview
+ Chapter 2-2: Data Dictionary Concepts
+ Chapter 2-3: Domains
+ Chapter 2-4: Files and Fields
+ Chapter 2-5: Work Fields
+ Chapter 3-1: Overview of APPX Processes
+ Chapter 3-2: Getting Started
+ Chapter 3-3: Process Definition
+ Chapter 3-4: Menu Processes
+ Chapter 3-5: Job Processes
+ Chapter 3-6: Input Processes
+ Chapter 3-7: Output Processes
+ Chapter 3-8: Update Processes
+ Chapter 3-9: Query Processes
+ Chapter 3-10: Inquiry Processes
+ Chapter 3-11: Status Processes
+ Chapter 3-12: Subroutine Processes
+ Chapter 3-13: Table Processes
+ Chapter 3-14: Automatic and Optional Children
+ Chapter 3-15: Using the Image Editor
+ Chapter 3-16: Using GUI Features of the Image Editor
+ Chapter 3-17: Using Event Points
+ Chapter 4-1: ILF Integration
+ Chapter 4-2: True/False Status Indicators
+ Chapter 4-3: Specifying Statements
+ Chapter 4-4: The ILF Editor
+ Chapter 4-5: The Appx ILF Debugger
+ Chapter 4-6: ILF Keyword Reference
+ Chapter 4-7: Predefined Fields
+ Chapter 4-8: Runtime Subroutine's and Predefined Processes
+ Chapter 4-9: Appx Chart Director API

Chapter 1-3: Data Dictionary

An Example of a Domain


One example of a domain might be employee number which should have the same number of characters and the same editing characteristics wherever it is used in a system. You can define such common attributes (including a descriptive name if desired); once, in an EMPLOYEE NUMBER domain. Domain attributes apply to all fields referencing that domain and cannot be overridden at the field level. Thus, any attributes that are not appropriate for each field based on the domain should be left blank in the domain definition. For instance, the employee master file may include employee number fields for both the employee and the employee's supervisor. While "Employee Number" is a good descriptive name for the first field, "Supervisor Number" is more appropriate for the second field. To accommodate this situation, just leave Descriptive blank in the domain definition and enter individual names instead. Meanwhile, both employee number fields remain subject to the same format and editing criteria defined for the domain.

Application Design Manual                                         "Powered by Appx Software"

40

©2006 By APPX Software, Inc. All Rights Reserved